Robotic Mowing of Separated Lawn Areas

ABSTRACT

A method of mowing multiple areas includes training a robotic mower to mow at least two areas separated by a space, including moving the robotic mower about the areas while storing data indicative of location of boundaries of each area relative to boundary markers, training the robotic mower to move across the space separating the areas, and initiating a mowing operation. Training the robotic mower to move across the space separating the areas includes moving the robotic mower to a traversal launch point of a first of the areas and moving the robotic mower to a traversal landing point of a second of the areas. The mowing operation causes the robotic mower to move to the traversal launch point, move from the traversal launch point across the space to the traversal landing point, and then mow the second of the areas.

TECHNICAL FIELD

This invention relates to mowing lawn areas and other areas with an autonomous robot, and more particularly to mowing multiple, discontiguous areas.

BACKGROUND

Autonomous robots can be programmed to mow lawn areas. Care must be taken to keep such robots from mowing outside intended areas. Buried electrical wires often define lawn boundaries that the robots are programmed to not cross. Other forms of navigation have also been considered.

SUMMARY

One aspect of the invention features a method of mowing multiple areas separated by a space. The method includes training a robotic mower to mow the areas, including moving the robotic mower about the areas while storing data indicative of location of boundaries of each area relative to boundary markers. The method further includes training the robotic mower to move across the space separating the areas, including moving the robotic mower to a traversal launch point of a first of the areas, storing data indicative of location of the traversal launch point, moving the robotic mower to a traversal landing point of a second of the areas, and storing data indicative of location of the traversal landing point. Initiating a mowing operation causes the robotic mower to autonomously, and in sequence: mow the first of the areas, move to the traversal launch point, move from the traversal launch point across the space to the traversal landing point, and then mow the second of the areas.

In some examples, the method further includes training the robotic mower to move across a second space separating the second area from a third area to be mowed. The method may also include generating a 2D grid of cells representing one or more of the areas and the space, and assigning a value to each of the cells. The value indicates whether a particular cell is mowable. The value may also indicate whether the cell is on one or more of the boundaries. The value may indicate whether the cell is along a path between the traversal launch point and the traversal landing point.

In some examples, training of the robotic mower to move across the space separating the areas is performed after training the robotic mower to mow the first of the areas and before training the robotic mower to mow the second of the areas. The mower and each of the boundary markers may include a respective wideband transceiver that operates from a frequency of 5925 MHz to 7250 MHz. Training the robotic mower to move across the space can further include storing data indicative of at least one intermediate position along a path between the traversal launch point and the traversal landing point, and initiating the mowing operation may cause the robotic mower to move along the path through the intermediate position.

In some cases, initiating the mowing operation may cause the robotic mower to mow the first area according to a mowing pattern determined in part by a shape of the first area. The mowing pattern may be a corn row pattern, for example. Initiating the mowing operation may cause the robotic mower to automatically conclude the mowing operation after mowing the second of the areas, without again mowing within the first of the areas.

In some embodiments, the traversal launch point is on the boundary of the first area. The traversal landing point may be on the boundary of the second area.

In some implementations, during the mowing operation the mower moves in a straight line from the traversal launch point across the space to the traversal landing point. During the mowing operation, the robotic mower may automatically disable a mowing function while moving across the space and then may reactivate the mowing function in the second area.

Another aspect of the invention features a robotic mower with a wheeled chassis, a motorized grass cutter carried by the wheeled chassis, and a controller. The controller is configured to store data indicative of location of boundaries of each of at least two areas to be mowed, wherein the at least two areas are separated by a space not to be mowed, store data indicative of a traversal path across the space not to be mowed, wherein a traversal launch point of a first of the areas and a traversal landing point of a second of the areas are located along the traversal path, and control the robotic mower to perform a mowing operation. In a mowing operation, the robotic mower autonomously and in sequence mows the first of the areas, moves to the traversal launch point, moves from the traversal launch point across the space and along the traversal path to the traversal landing point, and mows the second of the areas.

In some examples, the controller is further configured to move the robotic mower in a straight line from the traversal launch point to the traversal landing point. The controller can be further configured to train the robotic mower to move across a second space separating the second area from a third area to be mowed. The controller can also be configured to automatically disable the grass cutter while the robotic mower moves along the traversal path, and to reactivate the grass cutter once the robotic mower is in the second area. The controller may store data indicative of at least one intermediate position along the traversal path, and wherein the mowing operation causes the robotic mower to move along the traversal path through the intermediate position.

The controller may be configured to generate a 2D grid of cells representing one or more of the areas and the space, and assign a value to each of the cells. The value may indicates whether a cell is mowable, for example. The value may further indicate whether the cell is on one or more of the boundaries. The value may also indicate whether the cell is along a path between the traversal launch point and the traversal landing point.

In some implementations of the robotic mower, the controller trains the robotic mower to move across the space separating the areas after the robotic mower is trained to mow the first of the areas and before the robotic mower is trained to mow the second of the areas. The robotic mower and each of the boundary markers may include a respective wideband transceiver that operates from a frequency of 5925 MHz to 7250 MHz., for example. The controller may store data indicative of at least one intermediate position along the traversal path, and the mowing operation may involve the robotic mower moving along the path through the intermediate position.

Many lawns are not regularly shaped or composed of continuous grass regions. For example, a lawn may include multiple different mowable areas separated by a non-mowable area such as a path or driveway. In order to mow multiple discontiguous sections or areas of a lawn, the robot lawnmower described herein navigates between the separated lawn areas to mow the multiple areas.

In some examples, the robot includes a controller and sub-systems configured to guide the robot to traverse non-mowable areas separating a first lawn area from a second lawn area. In some cases the robot controls its sub-systems such that the cutting system is operable during a mowing operation and not operable during traversal of the non-mowable areas between lawn areas and bypass of a lawn area to travel to another lawn area. As a result, a single robot can be used to care for two or more physically separate lawn areas.

The system may further allow for automated methods, manual methods, or a selectable combination of automated and manual methods of training routes that the robot takes to complete mowing, bypass, and traversal operations and move between the lawn areas. The automated methods may include optimization techniques to increase efficiency of mowing operations. The user may also have the flexibility to override the automated methods with manual training methods.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1A is a schematic bottom view of an autonomous lawnmower robot.

FIG. 1B is a schematic side view of the robot of FIG. 1A.

FIG. 1C is a block diagram of a control system of the robot of FIG. 1A.

FIG. 2 is a schematic of an example set of discontiguous lawn areas with traversal regions that separate the discontiguous lawn areas.

FIG. 3 is a block diagram of a memory structure of the robot of FIG. 2.

FIGS. 4A-B are schematics illustrating methods of teaching boundaries of the discontiguous lawn areas to the robot.

FIGS. 5A and 5B are schematics illustrating methods of teaching traversal routes of the traversal regions to the robot.

FIG. 6 is a schematic illustrating methods of teaching bypass routes of the discontiguous lawn areas to the robot.

FIGS. 7A-B are the schematic of FIG. 2, each with a different overlaid route for the robot.

FIG. 8 is a screenshot of a computing device installed with an application to control the robot.

FIG. 9 is a flowchart for an example method of training the robot.

FIG. 10A-B are flowcharts for examples of operating the robot.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

The robotic lawnmower described below can mow discontiguous lawn areas as it autonomously moves about the lawn areas and crosses traversal regions or spaces that separate the lawn areas. The robot includes a cutting system with cutting blades to cut grass on the lawn areas as it moves along a lawn route (A “route” is hereby also referred to as a “path.”) via a drive system with wheels that mobilizes the robot. The cutting system is decoupled from the drive system such that the robot can deactivate the cutting system while the drive system is running. For example, while the robot follows traversal routes across the traversal regions between the lawn areas, the robot can deactivate the cutting system.

A controller is coupled to a memory storage element that stores the behavior of robot during various operations and the schedules for mowing the discontiguous lawn areas. In some schedules, the robot can be programmed to mow a target lawn area that is separated from the robot's current location. The robot can be programmed to move along bypass routes across the lawn areas with the cutting system deactivated so that the robot can reach a target lawn area without mowing the lawn areas that are in between the location of the robot and the target lawn area. The memory storage element further stores, for example, data corresponding to points or segments along the lawn routes, the traversal routes, and the bypass routes. A combination of manual training by a user or automatic path planning by subroutines programmed on the robot determines the routes, and the memory storage element can data pertaining to the routes.

FIGS. 1A-B are general schematic overviews of an example of the autonomous lawnmower robot 10, and FIG. 1C shows a block diagram of a control system that operates the autonomous lawnmower robot 10. FIG. 1A shows a schematic bottom view of the robot 10 with a forward direction F, which includes a main body 20 that contains wheel modules 610 a-b of a drive system 600 (shown in FIG. 1C) and a cutter 410 of a cutting system 400 (shown in FIG. 1C).

The wheel modules 610 a-b include the wheels, motor, and gearbox for driving the robot 10 in a forward or backward direction. The wheel modules 610 a-b can be differentially operated such that the robot can turn based on a level of drive supplied to each wheel. The drive system 600 further includes caster wheels 620 a-b that partially supports the weight of the robot 10.

The cutter 410 is, for example, rotatable reciprocating blades that can cut grass as a cutter drive sub-system 420 (shown in FIG. 1C) drives the cutter 410 to rotate. The cutter 410 has a mowing width WM that defines the width of grass that the robot 10 cuts as the robot 10 moves over uncut grass. The cutter drive sub-system 420 includes a high-power motor and a high-torque gearbox that operate the cutter 410 such that, at highest power, the motor, gearbox, and the cutter 410 can cut thick swaths of grass.

The bottom portion of the robot 10 can further include sensors part of a sensor system 650 (shown in FIG. 1C). These sensors may include cut edge sensors 510 a-b that differentiate between cut grass and uncut grass, grass height sensors that measure the height of grass beneath the robot 10, and cliff sensors that detect drop-offs in the terrain underneath the robot 10.

FIG. 1B is a schematic side view of the exemplary robot 10. The robot 10 includes a power system 800 with a power source 810, a controller 1000, a communication system 1100, and a memory storage element 900. The controller 1000 controls the systems of the robot 10, which will be described in more detail later in reference to FIG. 1C. The power system 800 supplies power via the power source 810 to the other robot systems. The communication system 1100 allows the controller 1000 to wirelessly communicate with external computing devices, such a mobile device or web-based device. The communication system 1100 can include, for example, a Bluetooth transceiver and/or a WiFi transceiver.

The power system 800, which includes a power source 810, provides power to the systems operable with the robot. The power source 810 is adjustable such that the power system 800 can provide a percent of full power. A charging system 820 within the power system 800 is connectable to an external charging dock to charge the power source 810.

The sensor system 650 (shown in FIG. 1C) of the robot 10 further includes a location estimation system 655 (shown in FIG. 1C). In some examples, the location estimation system 655 is a time-of-flight based system that uses a time-of-flight between a boundary marker (hereby also referred to as a “beacon” or a “marker”) and the robot to determine the pose of the robot. For example, boundary markers may be placed along the boundary of the lawn. While the time-of-flight system uses markers that have been described as boundary markers, the marker can also be placed within or near the lawn to aid localization of the robot lawnmower. In some cases, the boundary markers send out a signal that the robot lawnmower interprets to determine its position relative to the boundary marker. In other examples, the boundary markers are passive and a radiation source on the robot lawnmower emits radiation that reflects off surfaces situated in the lawn area and is detected by a radiation detector on the robot. The localization can use triangulation to determine the robot position within the boundary. The signals sent between the boundary markers and the robot positioned on the property allow the robot to estimate the angles and the distance by calculating time of flight to each of the boundary markers, and using trigonometry to calculate the robot's current position. In another example, rather than use time-of-flight measurements, the system can triangulate the distance to an object using a fixed-angle laser pointer and a CMOS imager, with a known baseline between the two. In such examples, the pixel location of the received signal at the imager is indicative of the distance to the object. In some particular examples, the boundary markers are wideband transceivers in the 5,925 to 7,250 MHz range or ultra-wideband transceivers. However, other time-of-flight transceivers could be used.

Moreover, the sensor system 650 includes an obstacle sensing system 657 that further includes the proximity sensors 680 disposed on the lateral sides of the robot 10 such that the robot can detect when it has made contact with a physical barrier or when it is in close proximity to a physical barrier. The proximity sensors 680 can take the form of contact sensors (e.g. a sensor that detects an impact of a bumper on the robot with a physical barrier) and/or LIDAR (Light Detection And Ranging, which can entail optical remote sensing that measures properties of scattered light to find range and/or other information of a distant target) sensors that detect when the robot is in close proximity to nearby objects.

The sensor system 650 also includes a handle sensing system 670 (shown in FIG. 1C), which detects when a detachable handle 675 is attached to the robot 10. The detachable handle 675 is usable in a training mode as well as a mowing mode. Other sensors of the sensor system 650 include a global positioning system (GPS) as an additional means to determine the location of the robot 10, a tilt sensor to detect the level of the terrain beneath the robot, a rain sensor to detect water from, e.g. rain, that could damage the electromechanical components of the robot 10, and sensors and encoders operable with other systems to assist in control of the robot 10. Additionally or alternatively, the sensor system 650 can include, but not limited to, wheel drop sensors, sonar, radar, etc., infrared cliff sensors, a camera (e.g., volumetric point cloud imaging, three-dimensional (3D) imaging or depth map sensors, visible light camera and/or infrared camera), etc.

Referring to FIG. 1C, to achieve reliable and robust autonomous movement and cutting, the robot 10 includes the controller 1000 that operates the memory storage element 900, the communication system 1100, the cutting system 400, the sensor system 650, the drive system 600, the navigation system 700, and the power system 800. The cutting system 400 includes the cutter drive sub-system 420, which can comprise a motor and gearbox to drive the cutter. The sensor system 650 further includes the handle sensing system 670 and the location estimation system 655 as well as other sensors mentioned earlier. The controller 1000 operates the navigation system 700 configured to maneuver the robot 10 in a path or route stored in the memory storage element 900 across the lawn areas and/or traversal regions. The navigation system 700 is a behavior-based system executed on the controller 1000. The navigation system 700 communicates with the sensor system 650 to determine and issue drive commands to the drive system 600. In particular, the controller includes obstacle detection and avoidance methods and behaviors implemented in response to sensor signals from the obstacle sensing system 657. The robot can use its proximity sensors to detect the general geometry of an obstacle in the general vicinity in front of the robot 10 so that the robot 10 can determine what direction to turn. For example, using proximity sensors 680 disposed on the front portion of the robot 10, the controller 1000 can determine when the robot is about to collide with an obstacle and communicate instructions to the navigation system 700 and the drive system 600 to avoid the obstacle.

The memory storage element 900 stores data pertaining to operations—such as mowing operations or traversal operations—and the subroutines of the robot that can be implemented for, for example, training or mowing operations. The data further includes lawn route data, traversal route data, bypass route data, path behavior data, and scheduling data all of which will be described in more detail later. The controller 1000 communicates with the memory storage element 900 to determine which systems to activate or deactivate during an operation. A system (e.g. the cutting system 400, the drive system 600, the power system 800) can be activated at a level from 0% (e.g., off) to 100%. The memory storage element 900 includes data associated with a level of activation for an operation. For example, in some operations such as traversal operations, the controller 1000 activates the power system 800 at a 50% activation level due to lower power requirements for the traversal operations. The controller 1000 can have a high power mode (e.g. 75%-100% activation level of the power system 800) to accommodate greater mechanical stresses in the cutting system 400 when mowing large and thick swaths of grass.

The electromechanical systems, including sensing, cutting, drive, navigation, power, communication systems, disclosed and illustrated herein may include the additional elements and features as disclosed in U.S. patent application Ser. No. 11/688,213, filed Mar. 19, 2007, titled “Robot Confinement,” the disclosure of which is incorporated by reference herein in its entirety.

In general, many lawns are irregularly shaped or composed of discontinuous grass regions. For example, a lawn may include multiple different mowable areas separated by a non-mowable area such as a path or driveway. In order to mow multiple discontiguous sections or areas of a lawn, the robot lawnmower described herein navigates between the separated lawn areas to mow the multiple areas.

FIG. 2 depicts a schematic view of an example of a property 100 with three discontiguous lawn areas 102 a-c. The lawn areas 102 a-c have boundaries 106 a-c, respectively. A traversal region 104 a separates the lawn area 102 a and the lawn area 102 b, and a traversal region 104 b separates the lawn area 102 b and the lawn area 102 c. The lawn area 102 a has a rose garden 125, which is an un-mowable feature (e.g., a keep-out or non-mowable space within the boundary of area 102 a). The traversal region 104 a includes a concrete walkway 115 that separates the lawn area 102 a from the lawn area 102 b and a floral divider 116 within the concrete walkway 115. Thus, if the robotic lawn mower is to mow both lawn area 102 a and area 102 b, it must cross the concrete walkway 115 in a region free of the floral divider 116. The lawn area 102 c has an amorphous shape with trees 127 located at segments of the boundary 106 c. The traversal region 104 b is a rocky area 117 that includes a circular fire pit 131. Thus, to navigate between lawn area 102 b and lawn area 102 c, the robot must traverse region 104 b while avoiding the fire pit 131.

The robot 10, shown parked at a charging dock 50, mows the lawn areas 102 a-c according to a schedule pre-determined by the user. The charging dock 50 restores the power source (described earlier) of the robot 10 and also serves as a launch point 1001 for route data that the robot stores (described later in more detail). The robot 10 can move from one lawn area to another via the traversal regions 104 a-b.

FIG. 3 shows an example of training data 303 stored in the memory storage element 900 (depicted in FIG. 1C) that the robot can execute to mow a discontiguous set of lawn areas. To train the robot 10, as will be discussed later, the training data 303 can be generated in automated methods, manual methods, or a combination of the two methods. The training data 303 includes boundary data 305, internal boundary data 310, traversal route data 315, bypass route data 320, lawn route data 325, path behavior data 330, and scheduling data 335. The controller 1000 (depicted in FIG. 1C) can process and execute at least some of the training data 303 to move about lawn areas and traversal regions and mow target lawn areas.

The boundary data 305 is the set of points that bounds a lawn area. Referring briefly back to FIG. 2, the boundary 106 a-c of the lawn areas 102 a-c can be represented by a set of discrete points stored as the boundary data 305 a-c, respectively, or as a set of labelled cells in a Cartesian grid, which will be described in more detail later. From the boundary data 305, the controller can determine geometric characteristics of the lawn area, including length, width, area, and shape.

The internal boundary data 310 is the set of points that bound obstacles that cannot be traversed. The internal boundary data 310 defines the keep-out zones within a mowable area where the robot lawn mower should not mow. For example, referring briefly back to FIG. 2 again, the rose garden 125 and the fire pit 131 can be represented by a set of discrete points stored as the internal boundary data 310.

The traversal route data 315, the bypass route data 320, and the lawn route data 325 each include a set of points. Each point stored in the traversal route data 315, the bypass route data 320, and the lawn route data 325 includes one or more locations (e.g. X-, Y-coordinates measured from one or more datum points). As will be described in greater detail later, the one or more datum points can correspond to locations relative to boundary markers placed along the boundary. The locations of the boundary markers serve as reference points for other points stored in the boundary data 305, the traversal route data 315, the bypass route data 320, and the lawn route data 325. Locations of points herein are generally measured relative to a coordinate system established relative to the boundary markers.

The controller can use the route data 315, 320, 325 to generate one or more paths of movements that the robot 10 follows as it executes mowing, traversal, or bypass operations. The points and the orientation angle can be measured with respect to a Cartesian coordinate system, defined by for example, Cardinal directions and a reference point on the lawn. The points correspond to a position of the robot, and the orientation corresponds to the direction that the front of the robot is facing. The controller can control the drive system and navigation system such that the robot is placed into the position of the point and the orientation associated with that point. The controller uses the points of the route data 315, 320, 325 to generate routes to move about the lawn areas and traversal regions.

Referring also to FIG. 2, the traversal route data 315 includes traversal route data 315 a and traversal route data 315 b for the traversal region 104 a and the traversal region 104 b, respectively. Generally, during a traversal operation, a robot starts on the boundary of a first lawn area, follows a route that crosses a traversal region, and ends on a second lawn area. In the example of FIG. 2, the controller uses the points stored in the traversal route data 315 a to generate a traversal route for the robot to move from the lawn area 102 a across the traversal region 104 a to arrive at the lawn area 102 b. The controller uses the points stored in the traversal route data 315 b to generate a traversal route for the robot to move from the lawn area 102 b across the traversal region 104 b to arrive at the lawn area 102 c. Traversal route data includes at least a traversal launch point and a traversal landing point. The traversal launch and landing points can be geolocations or positions (e.g., X, Y positions in a coordinate system) relative to the boundary markers. Traversal route data can further include intermediate traversal points.

The traversal launch points generally correspond to an end point of a first lawn route; the intermediate traversal points generally correspond to points in the traversal region where the robot travels (e.g., the path or the route); and the traversal landing points generally correspond to a start point of a second lawn route. The first lawn route terminates at a first interface between the first lawn area and the traversable region. The first interface is defined by a subset of points of the boundary data for the first lawn area.

The intermediate traversal points within the traversal route correspond to points that the robot follows while traversing the area. The intermediate traversal points can further correspond to other changes in behavior of the systems of the robot, such as the drive system, the power system, the navigation system, etc. For example, the controller could increase the power level at the intermediate traversal point in order to compensate for a change in terrain at the intermediate traversal point. The terrain could be more difficult for the robot to traverse after crossing the intermediate traversal point, and it would thus be beneficial to increase the power level of the power system. The intermediate traversal routes can include one or more additional intermediate points that, with the intermediate traversal points, can define line geometries that can be represented by two or more points. For example, two intermediate traversal points and an intermediate point can define an arc.

The traversal landing point corresponds to the end of the traversal region and may additionally correspond to a start point of a second lawn route. The second lawn route can begin at a second interface between the second lawn area and the traversal region. The second interface is defined by a subset of points of the boundary data for the second lawn area. The traversal route data 305 a includes a traversal launch point, intermediate traversal points, and a traversal landing point. The traversal route data 305 b includes a traversal launch point, intermediate traversal points, an intermediate traversal route, and a traversal landing point. The points described above for the traversal route data 305 a-b will be elaborated in more detail herein.

In some situations, it can be desirable to move to a different lawn area without first mowing the lawn area nearest to the robot docking station 50. In other situations, it can be beneficial to traverse a lawn area without mowing the area (e.g., to return to the docking station 50 from a separated lawn area). Bypass route data 320 a-b provides a path for the robot lawnmower to follow to traverse a particular lawn area without mowing the area.

The bypass route data includes the bypass route data 320 a for the lawn area 102 a and the bypass route data 320 b for the lawn area 102 b. Also referring briefly to FIG. 2, the points stored in the bypass route data 320 a allow the controller to generate a bypass route going from the launch point 1001 across the lawn area 102 a to the start of the traversal route for the traversal region 104 a. The bypass route data 320 b allow the controller to generate a bypass route going from the start of the traversal route for the traversal region 104 a across the lawn area 102 b to the start of the traversal route for the traversal region 104 b.

During mowing of a particular lawn area, the robot lawnmower can follow a predetermined path or pattern to complete cutting of the grass in the lawn area. The information about the path is stored as lawn route data. The robot lawnmower can store separate route data for each of the different lawn areas allowing each to be mowed according to a pattern that is appropriate for the lawn area. The lawn route data 325 includes lawn route data 325 a for lawn area 102 a, lawn route data 325 b for lawn area 102 b, and lawn route data 325 c for lawn area 102 c. The controller uses the lawn route data 325 a-c to guide the robot through movement patterns (described in more detail below in relation to FIG. 7) that cover the areas of the lawn area 102 a-c. The covered area of the robot is defined by the product of the mowing width WM (described above) and the length of distance traveled by the robot while executing a lawn route. The lawn route data 325 a-c each include a start point and an end point as well as the movement pattern for each lawn area 102 a-c, respectively. The controller can further compute the area of each lawn to determine the movement pattern. During a mowing operation, the computed area allows the controller to compare the computed area of the lawn to the covered area of the lawn to determine whether the robot has achieved enough coverage of the lawn. In some implementations, sufficient coverage is defined by a ratio of covered area to computed area greater than 1.

The path behavior data 330 indicates the operations of the robot systems (e.g. the drive system, the cutting system, the navigation system) along segments of the routes defined by the route data 315, 320, 325. For example, parts of or all of the routes corresponding to the lawn route data 325 can be associated with path behavior data 330 that instructs the controller to set the power system such that the drive system and the cutting system are both on and the grass is cut while the robot traverses the route. Parts of or all of the routes corresponding to the traversal route data 315 and the bypass data 320 can be associated with path behavior data 330 that sets the drive system to a predetermined drive speed (e.g., slower than mowing when the robot is likely to maneuver difficult turns or faster than during the mowing if the robot traverses a long distance) and the cutting system to an activation level of 0% (e.g., mowing is disabled). The path behavior data 330 can further include instructions to the navigation and/or drive systems to navigate the robot through turning and forward drive.

The scheduling data 335 can be set by the user via the mobile application or a user interface on the robot. The user can set a schedule that automates the robot to mow each lawn at a different time. For example, the robot can be set to mow lawn areas 102 a-b at a user-selected time on one day of the week and can be set to mow lawn area 102 c at another user-selected time on another day of the week. The scheduling data 335 determines which routes 315, 320, 325 to combine to generate a path for the mowing operation at the given time.

To generate the route data 315, 320, 325, the robot can be trained manually by a user or automatically. FIGS. 4-8 depict aspects of both automated and manual methods of training the robot. In particular, FIGS. 4A-C show different examples of generating the boundary data 305 that can be used by the controller or the user to generate the route data 315, 320, 325. FIGS. 5A-C show different examples of generating the traversal route data 315. FIG. 6 depicts an example of generating the bypass route data 320. FIG. 7 shows examples of route data (e.g., lawn route data, traversal route data, and bypass route data) that can be generated based on the results from FIGS. 4-6. As the route data 315, 320, 325 are generated, the path behavior data 330 can be automatically (described in association with FIG. 7) or manually (described in association with FIG. 8) associated with each of the route data 315, 320, 325 such that appropriate systems of the robot 10 are activated and deactivated. While the examples shown in each of FIGS. 6-8 are for the lawn areas and the traversal regions of the shown geometry, it should be understood that each training mode can be implemented to train the robot 10 for a variety of lawn geometries and configurations.

FIG. 4A shows an exemplary lawn area 102 c in which the robot 10 determines its pose within the lawn area 102 c by detecting boundary markers 128 a-c. Each boundary marker is positioned at a known location and situated so that the robot can detect each boundary marker as the robot navigates the lawn. To determine its position on the lawn, the robot receives signals from the individual boundary markers. The robot determines its pose based on the signals, which can represent the robot's location relative to the three boundary markers.

The pose of the robot (e.g., P₁, P2) can be determined based on the signals received from the boundary markers (e.g., a signal sent from the robot and reflected by the boundary marker or a signal generated by the boundary marker and received by the robot). The robot lawnmower determines the distance between the robot and the boundary marker based on the time-of-flight between the marker and the robot. Thus, based on the information from multiple boundary markers, the robot's pose can be determined by trilaterating based on received range/heading information from each of the boundary markers. In general, trilateration is the process of determining absolute or relative locations of points by measuring distances, using the geometry of circles, spheres, or triangles. In one example, trilateration can be based on a least squares algorithm using the distance/time-of-flight measurements. In another example, time-of-flight can be measured indirectly by measuring the phase shift between the signal and the receipt of the reflect signal. Alternately, distance can be determined by transmitting a signal from the robot, measuring the time the signal arrives at each boundary marker, and using a time-difference-of-arrival technique to estimate the robot's location.

The boundary 106 b is trained using a teach-and-playback routing in which the user pushes the robot around the boundary 106 b and the robot stores information about the location of the trained boundary. Further details of an exemplary process for determining the lawn boundary can be found, for example, in U.S. Ser. No. 14/512,098 filed on Oct. 10, 2014 and titled “Robotic Lawn Mowing Boundary Determination,” the contents of which is hereby incorporated by reference in its entirety.

FIG. 4B shows a manual process of generating the lawn boundary data for the lawn area 102 b. The user manually navigates the robot 10 around the boundary 106 b of the lawn area 102 b by guiding the robot 10 with the detachable handle 675, and the robot 10 generates the boundary data 305 b as it is moved around the lawn area 102 b. The user 70 manually maneuvers the robot 10 by pushing and pulling the handle 675. The robot 10 can automatically store points, or the user 70 can manually trigger a point to be stored. As the user 70 moves the robot 10, the robot 10 can be programmed to store the point corresponding to its current position route under the boundary data 305 b (described in reference to FIG. 3 above) for the boundary 106 b of the lawn area 102 b. In some implementations, the robot 10 can be programmed to automatically store its current position every second. The user 70 can also manually instruct the robot 10 to store its current position, via, for example, the application on the mobile device, which will be described in more detail later.

In some examples, a data processing unit generates a 2D grid of cells to represent the lawn areas. As the robot lawnmower determines its position relative to the beacons, the data processing unit determines and saves the coordinates of each cell containing the robot lawnmower during its motion. For each lawn area, each cell in the grid can be assigned a mowing-area value indicating whether the cell is understood to be NONMOWABLE (i.e. outside the boundary), MOWABLE (i.e., inside the boundary), or BOUNDARY (i.e., on the boundary). Each cell of the grid can be assigned (X, Y) coordinates based on a chosen origin (0,0) cell. Each cell can represent a square area, with each cell having a side length between 1 and 100 cm. For example, the grid can be a grid of cells, each 10 cm×10 cm. The robot lawnmower stores the (X, Y) coordinates of each cell traversed by the robot lawnmower along the actual teaching path travelled during the teaching mode. The robot lawnmower can mark the actual teaching path as a simple line tracing the path of the robot through single cells. Alternatively, the robot can mark all cells under the footprint of the robot as BOUNDARY cells. At the start of teaching, the values of all cells are initialized to NONMOWABLE. The operator presses the start button to start the training process and then drives around the boundary of the mowing area. As the robot drives, the values of all cells along its actual teaching path are set to BOUNDARY, the location of the cells being determined by the distance to the beacons. After walking the boundary, the operator presses a button to end the teaching process. Then, the operator positions the robot lawnmower anywhere within the mowing area and presses a button, indicating to the robot lawnmower that it is inside the boundary. In response, the system performs a flood fill to set the values of all cells inside boundary defined by the BOUNDARY cells to mark them as MOWABLE cells to be mowed.

Referring back to FIG. 3, the traversal route data 315 instructs the robot with a route to move across the traversal regions between the separated lawn areas, such as the traversal regions 104 a-b shown in FIG. 2. By way of general overview, to train the traversal route data, the controller determines and stores at least a traversal launch point and a traversal landing point. In some implementations, the controller further determines and stores intermediate traversal points. FIGS. 5A and 5B depict examples of points generated for the traversal route data 315 a and 315 b (described earlier in relation to FIG. 3), respectively. The traversal route data 315 a contain points that define a traversal route 1500 within the traversal region 104 a that the robot takes to move from the lawn area 102 a to the lawn area 102 b. The traversal route data 315 b contain points that define a traversal route 1600 within the traversal region 104 b that the robot follows to move from the lawn area 102 b to the lawn area 102 c.

FIGS. 5A-B show examples of the traversal routes 1500, 1600, respectively, generated for the traversal regions 104 a-b, respectively. During the traversal operation, the robot 10 navigates across the traversal regions 104 a-b by going sequentially through points that define the traversal routes 1500, 1600. The traversal route 1500 is defined by a first traversal launch point 1540, intermediate traversal points 1550 a-b, and a first traversal landing point 1560. The robot 10 moves sequentially in straight line segments from point 1540, to point 1550 a, to point 1550 b, to point 1560. Referring to FIG. 5B, the traversal route 1600 is defined by a second traversal launch point 1640, an intermediate traversal point 1650, and a second traversal landing point 1660. To move across the traversal region 104 b, the robot 10 moves sequentially in straight line segments from point 1640, to point 1650, to point 1660. While the example shown in FIG. 5C shows the traversal route data for particular configurations of the traversal regions, it should be understood that traversal route data can be generated for other traversable configurations of traversal regions.

In some examples, the route between the traversal launch point and the traversal landing point can be trained using a process similar to the process used to train the boundary of the lawn. For example, the user can place the robot into a traversal training mode and the traversal launch point can be the robot's location relative to the beacons. The user then pushes the robot along a path and the robot stores the path in a memory. The end of the path is stored as the traversal landing point.

While in the example described above, the traversal route was manually trained, in some examples an automated process can be used to train the traversal route. In an automated implementation of training the traversal route 1500, the controller automatically generates the traversal route 1500. Referring to FIG. 5A, the controller determines and stores the shortest traversable route between a source boundary (the boundary 106 a) and a destination boundary (the boundary 106 b). The robot 10 can identify the shortest traversable route in various ways. For example, the robot can identify locations where the robot is able to drive between one area and the other (e.g., determine regions free of obstacles). Given a grid-based representation of the lawn as described earlier, a path planning algorithm such as A*, rapidly exploring random trees (RRTs), or probabilistic roadmaps can then be used to find the shortest path from the robot's current location to the destination.

In a manual implementation of training the traversal routes 1500, 1600, the robot 10 is manually driven via a detachable handle (described earlier in relation to FIG. 4C but not shown in FIG. 5). When the user attaches the detachable handle to the robot 10 and notes in the application that the user is performing a traversal route training, the controller initiates a training mode. With respect to the traversal route 1500, the user navigates the robot 10 through the traversal route 1500, and the robot systems (e.g. the controller and the memory storage elements) generate points corresponding to the traversal route 1500. The robot systems, via the manual navigation of the robot 10, can generate points substantially similar to the ones described above, e.g., the traversal launch point 1540, the traversal landing point 1560, and the intermediate traversal points 1550 a-b, though it should be understood that the user can navigate the robot 10 along a different route with fewer or more intermediate traversal points. When the users pushes the robot 10 out of the region of the lawn area 102 a, the controller of the robot 10 confirms this departure and generates the traversal launch point 1540 corresponding to the point where the robot 10 exits the lawn area 102 a. The user of the robot 10 guides the robot through the traversal route 1500 turning to avoid the floral divider 116 and the robot 10 stores information about the path the robot 10 follows during the traversal route training. When the user pushes the robot 10 across the boundary 106 b, the controller can detect the crossing based on mapping data of the lawn 104 b and automatically generate the traversal landing point 1560.

With respect to the traversal route 1600, the user pushes the robot 10 across the boundary 106 b in a diagonal direction, and the controller generates the traversal launch point 1640. The user manually navigates the robot 10 toward the boundary 106 c avoiding the fire pit 131 and the robot 10 stores the path followed by the robot 10. When the robot 10 crosses the boundary 106 c, the controller generates the traversal landing point 1660 and completes the traversal route training for the traversal region 104 b.

In some examples, as noted above, the data processing unit generates a 2D grid of cells to represent the lawn areas and each cell is indicated as MOWABLE, NONMOWABLE, or BOUNDARY. In such a grid based system, during training of the traversal region, as the robot lawnmower determines its position relative to the beacons, the data processing unit determines and saves the coordinates of each cell containing the robot lawnmower during its motion (e,g., while traversing the boundary area between the lawn areas). Each cell of the grid can be assigned (X, Y) coordinates based on a chosen origin (0,0) cell. The robot lawnmower stores the (X, Y) coordinates of each cell traversed by the robot lawnmower along the actual teaching path travelled during the teaching of the traversal path. The robot lawnmower can mark the actual teaching path as a simple line tracing the path of the robot through single cells. Alternatively, the robot can mark all cells under the footprint of the robot as TRAVERSAL PATH cells.

At the start of teaching, the values of all cells between the multiple mowing lawn areas are initialized to NONMOWABLE. The operator presses the start button to start the teach process and then drives from one lawn area to another lawn area. As the robot drives, the values of all cells along its actual teaching path are set to TRAVERSAL PATH, the location of the cells being determined by the distance to the beacons. After walking the traversal path, the operator presses a button to end the teaching process. During operation, when the robot lawnmower traverses calls marked as TRAVERSAL PATH, the robot lawnmower disables (turns off) its cutting system.

FIG. 6 is an example of training bypass route data 320 a, 320 b, which provides data the controller uses to cross through the lawn area 102 a, 102 b, respectively. The controller generates a bypass launch point 1740 corresponding to the launch point 1001. The controller further generates a bypass landing point 1760, which coincides with the traversal launch point 1540. The bypass launch and landing points are locations relative to the beacons. The controller determines and stores the shortest route between the bypass launch point 1740 and the bypass landing point 1760 avoiding any keep-out zones within the lawn area. The controller selects initial points for the shortest route. The controller directs the robot 10 to move from the bypass launch point 1740 to the bypass landing point 1760 via the shortest route (e.g., a straight line). The controller knows the location of the rose garden 125 from the keep-out zone training of the mowable space and uses internal boundary data (e.g., internal boundary data 310 depicted in FIG. 3) for the rose garden 125 to determine a bypass route 1700 that avoids traversal of the prohibited space. As a result of this route determination, the controller stores the bypass launch point 1740, an intermediate bypass point 1750, and the bypass landing point 1760 as shown in FIG. 6.

Similarly, to train the bypass route data 320 b representing the bypass route 1800, the controller generates a bypass launch point 1840 that coincides with the traversal landing point 1560 and a bypass landing point 1860 that coincides with the traversal launch point 1640. The controller determines and stores the shortest route between the bypass launch point 1840 and the bypass landing point 1860 that avoids prohibited or keep-out areas (e.g., determines a path that stays within the mowable space). In other examples, a user can train the bypass routes in a similar manner to the process used to train the boundary by pushing the mower along a desired path while the robot stores information about the path.

In some examples, as noted above, the data processing unit generates a 2D grid of cells to represent the lawn areas, and each cell is indicated as MOWABLE, NONMOWABLE, or BOUNDARY. Regions between the lawn areas can have connection paths marked as TRAVERSAL PATH cells. In such a grid based system, during training of the bypass route, as the robot lawnmower determines its position relative to the beacons, the data processing unit determines and saves the coordinates of each cell containing the robot lawnmower during its motion (e.g., while traversing across the lawn area). Each cell of the grid can be assigned (X, Y) coordinates based on a chosen origin (0,0) cell. The robot lawnmower stores the (X, Y) coordinates of each cell traversed by the robot lawnmower along the actual teaching path travelled during the teaching of the bypass path. The robot lawnmower can mark the actual teaching path as a simple line tracing the path of the robot through single cells. Alternatively, the robot can mark all cells under the footprint of the robot as BYPASS cells.

At the start of teaching, since the bypass route is within the lawn area to be mowed, the values of all cells are MOWABLE. The operator presses the start button to start the teach process and then drives from one position within the lawn area to another position within the lawn area. As the robot drives, the values of all cells along its actual teaching path are set to BYPASS (or MOWABLE/BYPASS), the location of the cells being determined by the distance to the beacons. After walking the bypass route path, the operator presses a button to end the teaching process.

FIGS. 7A-B depict automatic generation of the lawn route data 325 a-c as well as the different path behaviors 330 associated with the route data 315, 320 generated above. The lawn route data 325 a-c includes a start point, an end point, and a movement pattern. The movement pattern can be, for example, a spiral pattern, a corn row pattern, zig-zag pattern, etc. A user can select a desired movement pattern for each of the lawn areas and different patterns may be selected for different areas of the same lawn.

In some examples, a yard may be too large to mow on a single charge of the robot lawnmower battery. In such situations, the robot can mow different areas of the yard at different times allowing the robot to return to the dock and charge its battery between mowing the different areas.

FIG. 7A depicts the execution of a mowing operation of lawn area 102 a, 102 b, after which the robot returns to the charging dock 50. FIG. 7B depicts the execution of a mowing operation of lawn area 102 c after which the robot returns to the charging dock 50. In the examples as shown, the lawn routes 1900 a-b are automatically generated based on the start points, the end points, and default movement patterns. For the lawn area 102 a, the robot is beginning at the launch point 1001 and proceeds in a corn row movement pattern until the robot has determined that it has covered the lawn area 102 a (e.g., completed the coverage pattern or determined that the covered area—defined by, for example, the distance covered by the robot multiplied by the width of the cutting element—is greater than 100% of the computed area for the lawn area 102 a). The corn row movement pattern guides the robot back and forth across the lawn such that the robot moves perpendicular to the longitudinal movement of the pattern slightly between each traversal. Upon completion of mowing of lawn area 102 a, to move from the lawn area 102 a to the lawn area 102 b, the controller executes the traversal route data 320 a which defines the traversal route 1500. The associated path behavior data 330 for the traversal route data 320 includes a deactivation of the cutting system. For the lawn route data 325 b, the start point is defined as the traversal landing point 1560, and the end point is defined as the traversal launch point 1640. Upon entry into lawn area 102 b, the robot activates the cutting system. After completion, the robot returns to the launch point 1001.

Referring to FIG. 7B, at a subsequent time (e.g., after charging) the robot continues to mow the lawn by mowing lawn area 102 c. To move from the launch point 1001 to the lawn area 102 c, the controller executes the bypass route data 320 a, the traversal route data 315 a, the bypass route data 320 b, and the traversal route data 315 b. The data 320 a-b, 315 a-b together define a bypass route 2100 to move the robot from the launch point 1001 to lawn area 102 c. The associated path behavior data 330 for the bypass route 2100 to bypass the lawn areas 102 a-b includes a deactivation of the cutting system. Upon entry into the intended area to mow, the robot activates the cutting system. The start point of the lawn route 1900 c corresponds to the end point of the bypass route 2100. The robot proceeds in a corn row movement pattern until the robot has determined that it has covered the lawn area 102 c. When the robot has determined that the robot has covered the lawn area 102 c, the controller directs the robot 10 to return to the launch point 1001.

As mentioned throughout this disclosure, the user can monitor and control various aspects of the robot and the training of the robot through an application installed on a computing device, which allows a user to enable functionality such as scheduling, bypassing, movement selection, lawn area selection, among other functions. The user can interact with the computing device via user interface features, such as a touchscreen display, a keyboard, voice command, gestures, or another type of interaction. While the computing device as shown in FIG. 8 is a smartphone, in other implementations, the device could be a portable device such as smart glasses, smart watch, a laptop computer, or a computing device such as a desktop computer.

FIG. 8 shows a screenshot of the user interface of the exemplary lawn area shown in FIG. 2. The mobile device displays a menu portion 3000 and a map portion 3500. The menu portion 3000 shows options including “Show Routes”, “Schedule”, and “Default Settings”. Tapping “Show Routes” on the menu portion 3000 will reveal the points or cells stored as a result of training the traversal routes, bypass routes, and lawn routes. As will be discussed, the user can interact with these points. Tapping “Schedule” allows the user to modify the schedule for the mowing operations of the robot. Tapping “Default Settings” allows the user to modify the default settings for the training subroutines.

The map portion 3500 includes a satellite map of the lawn areas that the user would like to mow. The satellite map can be selected by the user and can be downloaded from a map provider service. The processor of the mobile device can further recognize boundaries and delineations on the satellite map. Prior to any training, the user can interact with the satellite map to give a general area corresponding to the lawn areas that the user wishes to mow. The user can use the touchscreen to draw geometric shapes that function as virtual regions that can assist the robot in training. A user can set a virtual region as a lawn area, which can give the controller a general location for the boundary of the lawn areas. The user can further set virtual regions for the traversal regions and for obstacles. Also prior to training, the map includes the launch point 1001 corresponding to the location of the charging dock as well as the current location of the robot 10. The user can also select default settings for the training methods described herein.

As the user proceeds through additional aspects of training the robot (e.g. boundary training, traversal route training, and bypass route training), additional options from the main menu become available. After the robot has completed boundary training of the lawn areas, the map can include the points of the boundary data 305 (described above). While the traversal launch point and traversal landing point for each traversal region have been described as set automatically, the user can also override the automatically selected points by selecting one of the points of the boundaries shown on the map on the application. After the user selects traversal launch points and traversal landing points for each traversal region, the controller can further implement optimization algorithms (e.g. quasi-Newton methods) that consider the location of the traversal launch points and traversal landing points to compute the shortest route between the traversal launch points and the traversal landing points. In some implementations, the user can mark on the mobile device the boundaries that are traversable and non-traversable.

After a traversal launch point and a traversal end point for a traversal region are determined and stored, the user can initiate the automated or manual traversal route training described in detail earlier. As the mowing pattern can be defined after a lawn route start point and a lawn route end point have been defined, the user can also select the mowing pattern of each lawn prior to implementing the traversal route training.

The user can further create a schedule for the robot. Each area of the lawn can be separately scheduled. Thus, the robot stores scheduling data for each of multiple lawn areas. For example, if the user would like the robot to mow lawn area 102 c separately from lawn areas 102 a-b, the user can select the lawn area 102 c via the user interface and set a schedule (e.g. time and day of week) to mow the lawn area 102 c. The robot can be scheduled to mow the lawn areas 102 a-b in one mowing operation and the lawn area 102 c in another mowing operation. When the robot is scheduled to mow lawn area 102 b, the robot will follow the routes as described in FIG. 7A. When the robot is scheduled to mow lawn area 102 c, the robot will bypass the lawn areas 102 a-b to mow the lawn area 102 c, as shown in FIG. 7B.

FIG. 9 is a flow chart for training a robot to mow a first and a second lawn with a traversal region that separates the first lawn from the second lawn, such as lawn areas 102 a-b of FIG. 2. In general, the process involves identifying the boundary of the first lawn, identifying the boundary of the second lawn, selecting a traversal launch point, train first lawn route, selecting intermediate traversal points, selecting a traversal landing point, training a bypass route for the first lawn, selecting a movement pattern for the first lawn, and selecting a movement pattern for the second lawn area.

At step S900 the controller trains the robot to identify the boundary of the first lawn area. The controller implements one or more of the boundary training methods described with respect to FIGS. 4A-C to generate the points corresponding to the boundary of the first lawn area.

At step S905, the controller trains the robot to identify the boundary of the second lawn area. The controller implements one or more of the boundary training methods described with respect to FIGS. 4A-C to generate the points corresponding to the boundary of the second lawn area.

At step S910, the controller trains the traversal launch point. The controller can train the traversal launch point via a user selection on the application as described in FIG. 8, or the controller can implement route training (e.g., as described in FIG. 5) to automatically select the traversal launch point.

At step S915, the controller trains a first lawn route for the first lawn area. The first lawn area route uses a start point generally pre-determined by the location of a charging station and uses an end point determined by the traversal launch point trained in step S910. The controller selects a first mowing pattern for the first lawn route that can be a default pattern (e.g. corn row pattern) for the geometry of the first lawn area. The controller can further set the associated path behavior for the first lawn route.

At step S920, the controller trains the intermediate traversal points and the traversal landing point for the traversal region by implementing the traversal route training as described with respect FIG. 5A-B. The controller navigates the robot to the traversal launch point selected in step S910 and directs the robot through the traversal region as the controller implements the traversal route training. If there are obstacles within the traversal region, the controller can generate intermediate traversal points as the robot avoids the obstacles. As the robot crosses the traversal region and enters the second lawn, the controller generates the traversal landing point and thus completes the training of the traversal route. The controller can further set the associated path behavior for the traversal route including turning off the cutting system of the robot lawnmower.

At step S925, the controller trains a second lawn route for the second lawn area. The mowing pattern for the second lawn uses a start point generally determined by the location of the traversal landing point training in step S920. The mowing pattern for the second lawn uses an end point generally determined by the boundary points trained in step S905 and the traversal landing point. In some implementations, the end point is the boundary point farthest from the traversal landing point. The controller selects a second mowing pattern for the second lawn route that can be a default pattern (e.g. corn row pattern) for the geometry of the first lawn area. The controller can further set the associated path behavior for the second lawn route.

At step S930, the controller trains the bypass route to move from a launch point corresponding to the location of the charging station across the first lawn area to the start of the traversal route. The controller implements bypass route training described in FIG. 7 to generate the points of the bypass route. The controller can further set the associated path behavior for the bypass route.

FIG. 10A-B are flow charts for the mowing operations after the robot has been trained following the method of FIG. 9.

FIG. 10A is a flow chart of a mowing operation that mows both the first lawn area and the second lawn area. At step S1000A, the robot enables a cutting system of the robot and mows the first lawn area. The robot follows the first mowing pattern determined in step S915. After the robot has covered an area of at least 100% of the area of the first lawn, the mowing pattern ends at the traversal launch point determined in step S910.

At step S1005A, after the robot reaches the traversal launch point of the traversal route, the robot disables the cutting system and begins traversing the traversal region via the traversal route (including the traversal start point, the intermediate traversal points, and the traversal end point) determined in steps S910 and S920. The robot completes the traversal route at the traversal end point determined in step S920.

At step S1010A, after the robot traverses the traversal region, the robot enables the cutting system and begins to mow the second lawn via the second lawn route determined in step S925. The robot follows the second mowing pattern until the robot has covered an area at least 100% of the area of the second lawn area. The robot then terminates the second lawn route at the end point determined in step S925.

At step S1015A, after the robot reaches the end point of the second lawn route, the robot disables the cutting system and returns to the launch point.

FIG. 10B is a flow chart of a mowing operation that bypasses the first lawn and mows the second lawn area. At step S1000B, the robot disables a mowing function, bypasses the first lawn via the bypass route trained in step S935, traverses the first traversal region via the traversal route trained in steps S910 and S920 to reach the traversal landing point on the second lawn area.

At step S1005B, after the robot reaches the traversal landing point of the traversal route, the robot enables the cutting system and begins to mow the second lawn via the second lawn route determined in step S925. The robot follows the second mowing pattern until the robot has covered an area at least 100% of the area of the second lawn area. The robot then terminates the second lawn route at the end point determined in step S925.

At step S1010B, after the robot reaches the end point of the second lawn route, the robot disables the cutting system and returns to the launch point.

While the examples as described in this disclosure described three discontiguous lawn areas 102 a-c, in some implementations, the robot can be trained to mow more or fewer lawn areas. For example, in some implementations, the robot can be trained to mow a continuous lawn and consequently does not require traversal route data to move across traversal regions. In other implementations, the robot can be trained to mow several discontiguous lawn areas (e.g. four or more). The robot can be scheduled to execute several mowing operations at different times so that the power system of the robot can be sustained through the entire mowing operation. The robot can be trained to include several bypass routes that allow the robot to bypass lawn areas that are not to be mowed in a mowing operation.

While the combination of activation levels of systems have been briefly described (e.g. a 50% activation level of the drive system and 0% activation level of the cutting system during the traversal operations) for various operations, in some implementations, the setting of the activation levels can be adaptive. For example, as the robot executes training operations, the robot may have swath sensors that can detect the stiffness of grass that the robot passes over. As the robot detects the stiffness of the grass, it can modify the activation level of the cutting system during mowing operations to accommodate the stiffness. If the grass is stiff, then the activation level of the cutting system can be increased. The robot can further include torque or force sensors in the drive system to determine the level of activation for the drive system to drive the wheel modules to cross various terrains.

While the scheduling data 335 has been described to be set by the user via application on the computing device, in some implementations, the controller can be configured to automatically set the scheduling data. The controller can, for example, compute the area of each of the discontiguous lawn areas and the distance of potential routes, and use those computations to estimate an amount of power consumption associated with particular route options. The controller can then set a schedule of routes such that the robot can execute each mowing operation with a full charge of power.

While path planning algorithms such as A*, rapidly exploring random trees (RRTs), or probabilistic roadmaps have been described to be used to train the traversal and bypass routes, in other implementations, other algorithms, such as Floyd-Warshall algorithm, Johnson's algorithm, and Dijkstra's algorithm, can be used to reduce computational load. For example, in cases where the first set of points includes only one point or the second set of points includes only one point, a single source or single destination shortest path algorithm such as Dijkstra's algorithm can be used.

While the threshold mowing area coverage has been described to be 100% of the area of the lawn, in some implementations the threshold mowing area coverage can be greater. In other implementations, the threshold mowing area coverage can be greater than, for example, 150% of the area of the lawn area 102 a.

In the manual mode, while the robot has been described to detect the handle via the sensor system, in some implementations, the user can manually instruct the robot that the handle has been attached. Also in the manual mode with automatic point storage, the robot has been described to store a point every second. In other implementations, the duration of time between storing points can be modified by the user to be more or less. For example, for larger lawn areas, it can be beneficial to store fewer points in order to reduce the amount of storage space dedicated to the lawn route data.

While the handle 675 has been described as detachable, in other implementations, the handle remains on the robot but is collapsible or stowable. For example, the handle can be telescoping so that the handle can be collapsed into a small form factor when not in use.

Although virtual characteristics are not shown to define the lawn area 102 a-c, in some implementations, the user can use the application on the computing device to manually define general boundaries. The manually defined boundaries on the application can generate virtual markers that the robot follows to map the boundaries.

While the cells of the 2D grid of cells to represent the lawn have been described to represent a square area with side lengths between 1 and 100 cm, in other implementations the cells can be larger or smaller depending on the property. For example, for larger properties (e.g. a football field, a golf course), the side lengths could be between 1 and 10 m. In some implementations, the user manually sets the side lengths. In other implementations, the controller selects a cell size based on an input for the area of the lawn or property. In further examples, the controller implements an adaptive algorithm that determines the cell size based on the geometry of the lawn. For example, for amorphous lawn shapes, a larger number of cells can be used to reflect the amorphous geometry.

In some implementations, the user can select objective functions for the path planning algorithm. For example, instead of requesting a route with minimum distance between the traversal launch point and the traversal landing point, the user may select an objective function that the controller minimizes to select a route with the fewest number of turns, a route that begins and ends at specific points (e.g., the user pre-defines the traversal launch point and the traversal landing point). The user can also select more than one objective function to minimize. For example, the user may want to minimize the number of turns as well as the distance between the traversal launch point and the traversal landing point.

While the training method for the traversal routes 1500, 1600 and the bypass routes 1700, 1800 have been described to include one or less obstacles in between the respective launch and landing points, in some implementations, additional obstacles are detected during training. After generating the intermediate points and attempting the traversal or bypass route generated during the training, the controller determines the presence of an additional obstacle. The controller maps the additional obstacle and generates additional intermediate points to find an optimized path to avoid the obstacle. The controller continues to iterate through the training method until the controller directs the robot through a route without detecting an additional obstacle.

While the traversal launch points and traversal landing points have been described to selected in an automated manner or via the user application installed on the mobile device, in some implementations, the boundary markers placed along the boundary can also serve as traversal launch points and traversal landing points. In such implementations, as opposed to relying on virtual markers for the traversal launch and landing points, the user can place a physical marker (e.g., the boundary markers) that represent the traversal launch points and traversal landing points.

While the example of route segments shown in this disclosure focus on straight line segments between points, it should be understood that other curve geometries, such as arcs, can be generated with points on a route. Associating a polynomial with two points on a route can, for example, generate spline geometry connecting the two points. The controller, when the robot reaches one of the points of the spline geometry, can correlate the navigation system with the polynomial function such that the robot moves along the spline geometry. For example, for obstacles with geometries not easily defined by arcs, the controller can generate spline geometries to approximate a route to avoid the obstacle geometries.

While the first traversal launch points 1540, 1640 have been described as selected during the process training the traversal route, in other implementations, the default traversal launch point can be the charging dock.

While the lawn area 102 c has been described not to have a corresponding trained bypass route, in some implementations, the last lawn can have a trained bypass route that can be used as part of the return route. For example, during bypass route training, a bypass route can be trained for lawn area such that the robot can take the reverse of the bypass route in order to return to the charging station. Instead of using a traversal launch point for a traversal region for the end point of the bypass route that bypasses lawn area, the bypass route can use the end point of the mowing pattern for lawn area.

While the mowing pattern of a lawn route has been described to be complete after the coverage of the lawn, in some implementations, the controller can be programmed such that the mowing pattern of a lawn route terminates at the traversal launch point. For example, the end point of the lawn route can terminate at the traversal launch point of the traversal route.

In some implementations, the return route that the robot takes at the conclusion of a mowing operation can be a composition of bypass routes and traversal routes. For example, referring briefly to FIG. 7A, to return to the charging station 50 from the end point of the lawn route 1900 b, the robot 10 can follow the bypass route 1800, the traversal route 1500, and the bypass route 1700 in the reverse direction.

While the path behavior data 330 has been described to be assigned to the traversal route data 315 and the bypass route data 320 with respect to FIG. 7 after the lawn route data 325 has been generated, it should be understood that the path behavior data 330 can be generated as each route data is being generated. For example, as the points for the traversal route data and the bypass route data are being generated, the path behavior data associated with those routes can be set such that the drive system is set at a mid-range activation level and the cutting system is deactivated. In some implementations, the controller can be programmed such that training the bypass route data and the traversal route data automatically associates those route data with a deactivation of the cutting system, and training the lawn route data automatically associates the lawn route data to an activation of the cutting system.

While a lawn route described herein applies to a continuous lawn, in some implementations, a lawn can be segmented into two separate lawn regions contiguous lawn regions. The robot can be scheduled to mow the lawn regions at different times.

While the selection of the traversal launch point and traversal landing points have been described as an automated selection based on optimization of the distance of the traversal launch point from the traversal landing point, in some implementations, the modification of the traversal launch point and the traversal landing point can be a manual operation. For example, the user can view the boundary data stored for the lawn areas on the application of the mobile device and manually select locations for the traversal launch points and traversal landing points.

While the steps of the flow charts shown in FIGS. 9-10 have been described as occurring sequentially, it should be understood that some steps can be performed in a different order. For example, referring to FIG. 9, training the traversal route between the first area and the second area can occur after training the mowing operation for the first area and the second area. Training the bypass route can occur before training the second lawn route or training the traversal route.

A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. 

1. (canceled)
 2. An autonomous lawnmower robot comprising: a drive system to move the robot about mowable areas; a cutting system to mow the mowable areas as the robot moves about the mowable areas; and a controller to initiate a first mowing operation in accordance with a schedule to mow a first mowable area of the mowable areas, and initiate a second mowing operation in accordance with the schedule to mow a second mowable area of the mowable areas.
 3. The robot of claim 2, wherein: configurations of the controller to initiate the first mowing operation in accordance with the schedule to mow the first mowable area comprise configurations to initiate the first mowing operation at a first scheduled time and a first scheduled day in accordance with the schedule, and configurations of the controller to initiate the second mowing operation in accordance with the schedule to mow the second mowable area comprise configurations to initiate the second mowing operation at a second scheduled time and a second scheduled day to initiate the second mowing operation.
 4. The robot of claim 2, wherein the controller is further configured to transmit data indicative of a map of the first mowing area and the second mowing area to cause a remote user computing device to present a graphical representation of the map.
 5. The robot of claim 2, wherein the controller is configured to initiate a third mowing operation in accordance with the schedule to mow the first and second mowable areas of the mowable areas.
 6. The robot of claim 5, wherein configurations to initiate the third mowing operation in accordance with the schedule to mow the first and second mowable areas comprise: configurations to initiate the third mowing operation in accordance with the schedule to mow the first mowable area, move across a space separating the first mowable area and the second mowable area without mowing the space, and mow the second mowable area.
 7. The robot of claim 2, wherein configurations of the controller to initiate the second mowing operation in accordance with the schedule to mow the second mowable area of the mowable areas comprise: configurations to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area, and mow the second mowable area.
 8. The robot of claim 7, wherein configurations of the controller to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area further comprise: configurations to initiate the second mowing operation in accordance with the schedule to move through the first mowable area and then through a space separating the first mowable area and the second mowable area, without mowing the first mowable area and the space, to arrive at the second mowable area.
 9. The robot of claim 2, wherein the controller is further configured to store data indicative of the schedule to initiate the first mowing operation and the second mowing operation.
 10. The robot of claim 2, wherein the controller is further configured to receive, using a wireless receiver of the robot, data indicative of the schedule to initiate the first mowing operation and the second mowing operation.
 11. The robot of claim 10, wherein configurations of the controller to receive the data indicative of the schedule comprise configurations to receive the data from a user computing device.
 12. The robot of claim 2, wherein the controller is further configured to initiate a docking operation after the second mowing operation to move the robot toward a docking station through the first mowable area without mowing the first mowable area.
 13. The robot of claim 2, wherein the controller is configured to generate data indicative of the schedule to initiate the first mowing operation and the second mowing operation based on at least one a power consumption estimate to mow the first mowable area or an estimate of a power consumption estimate to mow the second mowable area.
 14. A method comprising: presenting, by a user computing device, a graphical representation of a map of mowable areas; and transmitting, by the user computing device, data indicative of a user-selected schedule to initiate mowing operations of an autonomous lawnmower robot, wherein the data indicative of the schedule comprises first data to cause the robot to initiate a first mowing operation of the mowing operations in accordance with the schedule to mow a first mowable area of the mowable areas, and second data to cause the robot to initiate a second mowing operation in accordance with the schedule to mow a second mowable area of the mowable areas.
 15. The method of claim 14, wherein the data indicative of the schedule comprises data indicative of a first time and a first day to initiate the first mowing operation and a second time and a second day to initiate the second mowing operation.
 16. The method of claim 14, wherein the data indicative of the schedule comprises third data to cause the robot to initiate a third mowing operation in accordance with the schedule to mow the first and second mowable areas of the mowable areas.
 17. The method of claim 16, wherein the third data is configured to cause the robot to initiate third mowing operation in accordance with the schedule to mow the first mowable area, move across a space separating the first mowable area and the second mowable area without mowing the space, and mow the second mowable area.
 18. The method of claim 14, wherein transmitting the first data to cause the robot to initiate the first mowing operation in accordance with the schedule to mow the first mowable area and the second mowable area comprises: transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area, and mow the second mowable area.
 19. The method of claim 18, wherein transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area comprises: transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move through the first mowable area and then through a space separating the first mowable area and the second mowable area, without mowing the first mowable area and the space, to arrive at the second mowable area.
 20. A system comprising: a computing device comprising: a user interface; a memory configured to store instructions; and a processor to execute the instructions to perform operations comprising: presenting, using the user interface, a graphical representation of a map of mowable areas; and transmitting data indicative of a user-selected schedule to initiate mowing operations of an autonomous lawnmower robot, wherein transmitting the data indicative of the schedule comprises transmitting first data to cause the robot to initiate a first mowing operation of the mowing operations in accordance with the schedule to mow a first mowable area of the mowable areas, and second data to cause the robot to initiate a second mowing operation of the mowing operations in accordance with the schedule to mow a second mowable area of the mowable areas.
 21. The system of claim 20, wherein the data indicative of the schedule comprises data indicative of a first time and a first day to initiate the first mowing operation and a second time and a second day to initiate the second mowing operation.
 22. The system of claim 20, wherein transmitting the data indicative of the schedule comprises transmitting third data to cause the robot to initiate a third mowing operation in accordance with the schedule to mow the first and second mowable areas of the mowable areas.
 23. The system of claim 22, wherein is configured to cause the robot to initiate third mowing operation in accordance with the schedule to mow the first mowable area, move across a space separating the first mowable area and the second mowable area without mowing the space, and mow the second mowable area.
 24. The system of claim 20, wherein transmitting the first data to cause the robot to initiate the first mowing operation in accordance with the schedule to mow the first mowable area and the second mowable area comprises: transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area, and mow the second mowable area.
 25. The system of claim 24, wherein transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move from the first mowable area to the second mowable area without mowing the first mowable area comprises: transmitting the second data to cause the robot to initiate the second mowing operation in accordance with the schedule to move through the first mowable area and then through a space separating the first mowable area and the second mowable area, without mowing the first mowable area and the space, to arrive at the second mowable area. 